More Pages: Commerce Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100


Advice you can understand and use
Principles & models cut through complexityIt starts with an extremely brief, but informational, description of the characteristics of e-business and some of the challenges and opportunities that set it apart from an architectural requirements standpoint. This is followed with an in-depth discussion of the "essence of architecture" that sets the tone and pace for the rest of the book. I like this because there is a vast difference between a definition, which can be succinctly described, and an essence, which is more a philosophy. The philosophy given by the author is sensible and lays the foundation for the principles and seven steps of defining the architecture that follow in later chapters. Especially valuable is way architecture is broken down into views: component, design, blueprint and framework. Also included in the essence section are two chapters, one addressing object-oriented methods and the other on project scope. Each contained a wealth of information and some sound points of view and advice. Regardless of your knowledge or experience I recommend reading through these two chapters because of the fresh ideas that pop up throughout them. It forced me to see things in ways that I do not normally observe.
The seven-step solution building process encompasses the eight chapters of Part II. The first chapter, introduction, gives guiding principles and these are worth printing on a large poster and memorizing. The process itself is (1) business modeling, (2) IS modeling, (3) Current IS analysis, (4) IS architectural planning, (5) implementation planning, (6) deployment and (7) review. In one respect there is nothing new or unique about this process, but the value in reading through each of the chapters is how clearly the approach is described and how the supporting information is developed. The writing here (and illustrations) exemplify clarity. I gained a lot, too, from the many lists and tables.
Part III is titled "Let's Get Practical" and is where the author ties together loose ends by addressing the use of consultants, methodologies (good and bad) and reuse. There is a lot of wisdom and advice here as in the rest of the book - much of it delivered with humor and always with good sense.
Overall, this is an excellent book. It's well written, filled with information and puts you in the right frame of mind to tackle architecture in a methodical manner. What it does not do is provide technical details or espouse any particular product or technology - there are other books for that.
Sound principles, successful approach and common senseFirst, the principles and approach really are aligned to e-business although they can also be applied to any system or enterprise application. Second, the book may appear to be basic, but the author manages to get you think out of the box every step of the way. An example is the scope-trade off discussion in chapter 4 where you are shown an illustration of a road improvement project that depicts an ideal (and not so feasible) solution and some alternatives. In a single, simple illustration and a few paragraphs the whole concept of scope trade-off crystallizes and comes into sharp focus. Another example is a text box on page 37 that describes how the author and his wife, both IS professionals, attempted to devise a check book system for personal use. The story drives home the fact that even professionals and prime stakeholders can get requirements wrong.
Among the things I like most are: the seven-stage process itself and associated principles, which make you step back and look at architecture as its most basic level; the discussion of architecture and its relationship to object-orientation is one of the best compare and contrast pieces on the topic I've read; and the discussion on component-based software engineering is concise and completely aligned to that approach to both e-business in general and architecture in particular.
This book reminds me of those written by Gerald Weinberg on that it focuses on deeper aspects of a subject than mere technology. True, the technical aspects of this book are lightweight, but the underlying principles and approach are anything but. If you're seeking low-level technical information on architecture pass this by. If you want to read a book that will inspire you to think out of the box, organize the important elements of architecture and infuse massive doses of common sense, this book is a treasure and has my highest recommendation.


Balanced Look at E-Commerce Business and Technical ProcessThis text looks at business trading over the Internet from a process perspective. Marketing and Web page development are mentioned, but the focus of the content is on the technological "hoops" that are jumped through in order to complete e-commerce transactions.
The book includes chapters on Internet development history, packet-switching, server hardware and software considerations, security issues, payment systems, and marketing strategies (including the development of a business plan).
Instructionally, this book is current and a quality read (a little dry perhaps, but consider the material). The authors use many examples throughout and include many company and product names.
For someone in IT or management, this is a wonderfully balanced survey of e-commerce business structure and transaction process. The material presented will thoroughly get the reader up to speed on all of the aspects of ecommerce including most of the non-technical and semi-technical terminology. This really bridges the gap between IT professionals and traditional managers.
I feel that this is one of the better books I've ever used and recommend it highly for managers or instructors.
Best and Most Current Textbook AvailableThe book offers a balanced business-technology approach to the subject of e-commerce and include a great overview of both relevant technologies and business/revenue models. The book includes important issues like legal and international concerns and even has a great little section on managing and staffing Web development projects in the last chapter.
This is the only book on e-commerce that I have seen that actually creates and uses a theory-based organizing framework (they build on Porter's work on value chains). Even though the book was clearly designed to be used in the classroom (it has problem assignments, exercises, and an extensive list of references at the end of each chapter), I think this book would be an excellent resource for a business manager that wanted to learn what all of this e-commerce stuff was all about OR for a techie that wanted to learn something about the business end of e-commerce.
The book is a very easy read and is remarkably interesting (even the chapter on security theories is pretty hard to put down... and that is some dull stuff, usually). The book includes bolded company names throughout and each of those names is included on the book's Web site as a hyperlink to the company site. This is very useful because you can see the examples that the book mentions come to life (if you can read the book while you're in front of your computer)...
I would recommend this book to any reader that wants to learn more about electronic commerce than you would find in a light overview book. This book gets into details, but in a very readable way.
a good textbook

Highly RecommendedOn the downside there are several minuses which will hopefully be corrected in a future edition
1. The UML diagrams are incorrect, in that they nearly all have the aggregation symbol at the wrong end
2. The fact that the book was written by several authors shows, in that the same idea shows up in several places in the book, without correlation. Not that there's anything contradictory about that. It would be nice if the different "definitions" or explanations were somehow collected in one place. For example, there's two discussions of security servers, with neither one aware of the other. The second discussion (p. 331-332) is not even referenced in the index.
3. There's very little discussion of performance issues. This is a particular sore point, considering they spend considerable amount of space discussing (even promoting) EJB security with no mention of its downside (its too slow)
All in all, though, I highly recommend this book be read by architects, and app developers as well as product managers before diving into security development for your application
Practical guide for security of enterprise solutionsContrary - it explains how application must be design to prevent unauthorized access to sensitive data. It is a reality that modern application being build on distributed technologies actually provides more services for the data that enterprise already has. It is a bonus and a threat, because it is another hole for an attack. This book explains how defend in this situation. Must have for project managers of EIS integration.
Book contains not just general ideas - it is a practical guide and somehow a reference for different approaches to security for EJB and CORBA.
Unique chapters are about integrating of EJB and CORBA security. This is a reality that different technologies co-exist and it can work for you or against of you.
I would recommend this book to s/w architects, project managers and professionals working on enterprise systems integration.
A must have for a security engineer

A good overview of the theory as well as technoogy behind EC
Early e-commerce thought leadership
Very Comprehensive book on all Facet of E-commerce

Sometimes wanting to do the "right thing" isn't right.
The Best Book in the World. And I mean it.
Almost as good as the Necromennon

What went wrong... but also what went right"Dot.bomb," however, also examines the dotcom enterprises that succeeded, such as eBay, Priceline and our dear old Amazon. What made these ventures an exception is a major thrust of the book -- and perhaps the most informative. It also provides a light at the end of the proverbial tunnel for the reader weary of failure stories.
Since the latest examples in the edition I read were from early 2001, one hopes that a newer edition would bring the dotcom story up to date. How the Internet industry has responded to the recession, corporate scandals and 9/11 are tales that an updated version of "Dot.bomb" ought to cover.
Good, critical look at the big implosionThis is an interesting companion to David Kuo's book. With a very similar title, Kuo is funnier and more dramatic, primarily because valueamerica.com was such a huge, single implosion and Kuo, by training, is a writer and, to some degree, a spin doctor. More serious and critical, Carton pulls no punches, examines a lot more companies, and has a more technical, well-grounded understanding the business models (or lack thereof) that created and destroyed the late 1990's version of the new economy. Start with "the greater fool" theory. Carton's book is better for the serious student wanting to see the big business picture.
Carton is methodical and crisp, even dry at times. The graphics of the book, including the font and page layout, could also have been more appealing or reader-friendly. If you're teaching an e-commerce course, as I have, you want to consider Dot.Bomb.
Now is the time to learn from our "new-economy" mistakes

Irony in the title, a good read in between the covers
Solid advice, fun to read
Where Have All the Dot.coms Gone?

Good Roundup, Difficult Interface
Excellent undergraduate textbook and overviewThe appendix material on HTML is not needed in the book. Anyone interested in that topic is probably going to buy another more complete book on the topic (perhaps even another Deitel book).
The biggest problem, though, is that this book is becoming very dated. It was made available in 2000. Much has changed since then. Most textbooks of this sort are updated every 2 years. This one needs to be updated to a second edition.
e-Business & e-Commerce management clearly explained.

Helpful but a bit vague(1) Understanding customer's values, wants and needs
(2) A few ideas on deciding how much your customer is worth
(3) Earning money from your e-customers by understanding the concept of lifetime value
(4) The different types of models out there for web business
(5) How different generations, men, women, children vary in their respective shopping habits and ways we could capitalize on them.
(6) The need to track and collect data on e-customer's profiles
(7) The importance of convincing the e-shopper's decision to come to your site
(8) Thoughts on up and coming shopping habits such as mobile e-commerce
(9) Ways to attract your customer's attention while they are visiting your website
(10) The importance of respect and the need to provide a human touch
This book is an interesting read on all these areas. Unfortunately, a lot of effort was wasted on explaining in very vague terms why these areas are important instead of providing any new insights or practical solutions....
An expanding vision of the e-universe
If Mckeown truly is a guru that makes me a follower

Not Very Nautical Masters ThesisShould you want all of the details as to how the conclusions were arrived at along with some fairly illustrative diagrams and sketches, this book might be of some interest. It also has a good survey of the very un-nautical Narmer Palette.
Contrary to the dustcover (on which, ahem, someone seems to base her reviews in lieu of actually reading the book), only one shipwreck is discussed and even that is mentioned only in the final chapter, the only part of the book that focuses specifically on seafaring.
From Egypt to Mesopotamia
important contribution for serious readers
Many of those alternatives are embodied in this book, which was written at the level of managers rather than those who construct the IS solutions. Some of the solutions, such as always make sure you hire and retain good people are slightly above the level of "duh", and yet in many cases the simple is the most overlooked.
The emphasis throughout is on architecture and strategy. With the rapid pace of e-business development, where you can flame up and flame out in weeks, you must build your systems so that they are as open ended on the high side as possible. The advice put forward here is a prescription for sound management of what is now the most complex of all the mandatory facets of a business. Furthermore, there are also several places where the author puts forward danger signals to help identify whether analysis paralysis is setting in.
There is one excellent example concerning how to create solutions. When presented with a problem about shortening a winding road, there is the simple solution of connecting the endpoints. However, if it is necessary to visit the intermediate points on the old road, this solution is hardly optimal. Sometimes incremental, seemingly partial solutions are the most effective.
If you are a manager looking for guidance in how to start, build, maintain or expand an e-business structure, then this book will help a great deal. No magic formulas or absurd hype, just sound fundamental principles that will improve your chances for success.